home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
QRZ! Ham Radio 6
/
QRZ Ham Radio Callsign Database - Volume 6.iso
/
pc
/
files
/
p_baycom
/
4thbyap.exe
/
BYAP.DOC
< prev
next >
Wrap
Text File
|
1993-02-20
|
10KB
|
251 lines
I have added all calls that have given any kind of feedback
from previous versions as list of "registred" users. (All that
I have been able to track having a "home bbs" by messages that
I have saved, there might be some missing ones).
Information of this release have been sent to them as private
message (should be there ages before @ww bulletin!).
I'll thank all of you very much. Because of this feedback I have
now produced this new version, otherwise it might not have been
done.
I hope there are no (big :-) ) bugs. Anyway, save the old version
while testing this one. I was also usefull one.
It might be that there will be new Baycom out with Yapp soon. In
that case this will be the last version, otherwise I'll continue
developing these programs (if I receive some feedback)
What is new ? 17-02-1993
ByapC v1.3
ByapT v2.1
- when file to be sent was on different drive (I.E. A:file.exe)
the drive and path was added to yapp.snd causing an incorrect
YPUT parameter for bbs. Now only the name is transferred to
yapp.snd. (ByapT)
- when requested file is not found and DIR_MASK has been given
and directory list executed will now ask:
"ESC to end program"
previously CTRL+BREAK did not work on all machines. ESC works,
I hope so.....(ByapT and ByapC)
- added config file where you can tell where to keep temoporary
YAPP.* files. NOTE ! You have to set SCC.INI macros to point
to SAME drive/subdir as here. And remember: You CAN NOT use
C:\BAY\FILE\ with ST macros ! Instead USE C:/BAY/FILE/ it
is accepted.(ByapT and ByapC)
In same config file you can point drive and path for competely
correct decoded file (ByapC).
Both drives/subdirs are tested at programs begin. If test
fails current drive and path is used instead.
Detection cant clear out if floppy is missing and path is
given to floppy's root directory. In that case error will
be created ("cant open") when program tries to write empty
floppy station.
Also upload command , default YPUT, and description line
exist/not exist, default exist, can be defined in BYAP.CFG
for YAPP.SND file (ByapT)
- it was bossible to add old YAPP.IN to YAPP.BRK (resume case).
To prevent these accidents ByapC will now ALWAYS rename input
file (what ever it is, mostly YAPP.IN) to same name and extension
".BAK". This is done no matter if decoding was succesfull or not.
If there is file using same name and extension BAK it will be
deleted before rename. (as EDLIN and most editors do....)
(ByapC)
- Input file name can NOT contain characters "*" and/or "?"
(ByapC ans ByapT)
and extension can NOT be ".BAK"
(ByapC )
- ByapC (S)tandard function did fail with some other BBSes than
FBB because different header (than descripted in Rev 1.1 Yapp
document of WA7MBL 06/23/86).
Now header detection routine has been rewritten. I hope it can
now detect those "other-than-fbb" headers as well as FBB ones
(ByapC)
- it was bossible to decode YappC capture using (S)tandard. This
was bossible because poor data-block detection.(maybe it was
rather good anyway...hi).
Now block detection is better and attempt to decode YappC with
(S)tandard gives error.
(ByapC)
- disk read and write errors (disk full) are now better detected
and reported.
(ByapT and ByapC)
----------------------------------
BYAPC v1.2 OH1KH @ OH1RBF.FIN.EU
& BYAPT v2.0 @ UO22
20-01-1993
Here are the latest versions of Baycom Yapp receive and transmit processing
files.
Some bugs have been corrected (thanks for reports!), some may still remain.
I'll hope not, but......
Both programs are now designed so that they are able to work from Baycom's
DOS-SHELL (:o). This, with keyboard macros, is making Yapp transfers nearly
as easy as the feature would be "built-in".
Note that you may place these programs in any subdir you wish, as long as
also incoming and outgoing data is directed to same subdir. Of course
ST-macros have to be corrected to point right subdir.
Both programs give short help (with ?) mainly how to operate Yapping
manually. How ever ST macros should be used in every case. This saves
lot of typing.
---------RX:---------
Go to FBBDOS and give command YGET FILENAME. BBS will answer " Ready to
send FILENAME with ........".
At this point press ALT-A.
Capture is opened and start chrs are sent to BBS. Look at byte
counter on right side, bottom statusline.
When this counter gets nearly same value as FILENAME length was, look
for the last characters from BBS. They should be ^C^A (inverse or
different color meaning they are controls.)
When ^C^A has been received, press ALT-S.
Capture is closed and ByapC is started (Dos-shell). It defaults to
YAPP.IN capture filename. If that is OK just press enter. Otherwise
give an other name.
Next question is protocol. If your ST-macro sends ^F^A^F^F with ALT-A
give "C" here for YappC. If the macro sends ^F^A^F^B, give "S" for
standard Yapp. It is recommended ALWAYS to use YappC when bossible.
If your YAPP.IN holds data from RESUME give "J" for joining resume data
to previously received data. Resume works ONLY with YappC !
--RESUME---
When you have entered one of those 3 letters ByapC will start decoding.
If any errors are detected (and YappC used) it will create YAPP.ERR
and YAPP.BRK files.
In this case , when back in FBBDOS, give same YGET FILENAME again to
request resume for corrupted file. When BBS says "Ready to send....."
Do NOT press ALT -A !"
INSTEAD OF THAT PRESS ALT-D !! Immediately (1sec) after that press
ENTER.
This ALT-D will send first resume request from file YAPP.ERR. After
ENTER is pressed new capture is opened. If this happens too late
header information is lost, and capture is useless. Then try again.
Again, when data transfer ends (^C^A as last chrs). Press ALT-S as
usually. Capture is closed and ByapC is started.
Now give filename(or Yapp.in for default) and THEN PRESS "J" for
joining data.
If all goes OK, file is ready. Otherwise new YAPP.ERR and YAPP.BRK
are created for next try.
--------------TX:-----------------
Yapp transmit is supported only as standard Yapp.
Go to FBBDOS. Select upload directory.
Press ALT-Q, BYAPT is started asking file name to transmit.
Give the name and description (max 40chr) and ByapT will process file
for transmit to YAPP.OUT. File YAPP.SND holds commands YPUT FILENAME and
DESCRIPTION LINE. YAPP.HEA holds the header info of file.
When BYAPT finishes, YAPP.SND will be sent via same ALT-Q macro.
BBS will reply "Ready to receive....."
Then press ALT-W to send transfer start characters.
BBS will reply ^F^A
At that point press ALT-W to send header info.
When it has gone BBS will send ^F^F
Then press ALT-R to send YAPP.OUT, the data of file. Look after transfer.
If "Abort" with some control chars appear while transfer is still going
on, close buffer (:WPRG OFF) and start from beginning.
When all data has gone BBS will send ^F^D.
Then press ALT-T to terminate Yapp transfer.
-----------------------------------
That's all. Rather easy, isn't it. Here you will have a proposal
for your ST-MACRO definitions. Add this to your SCC.INI file
with necassary modifications.
Happy Yapping !
73'Saku OH1KH
; Definition of the Standard Texts.
; --------------------------------
; proposal, make your own changes as needed !
;--------------------------------------------
;
; YAPPC Start RX1 --> reply to ^E^A (alt-a)
st a0 \x:paclen 4 ;set paclen to 4 for next transmission
st a1 wprg yapp.in ;open capture "YAPP.IN"
st a2 \x ;send ^F^A^F^F (For YappC, ^F^A^F^B for standard)
;
; YAPPC stop RX2 --> reply to ^C^A (alt-s)
st s0 \x ;send ^F^D
st s1 \x:wprg off ;close capture
st s2 pacl 230 ;set paclen to normal
st s3 \x\rbug ;send dummy cmd to fbb to break looping (perhaps)
st s4 \x:o BYAPC ;goto DOS-shell for ByapC process.
st s5 \x ;clean line
;
; YAPPC resume --> reply to ^E^A (alt-d)
st d0 :rprg yapp.err ;send received info + request to resume
st d1 :wprg yapp.in\i ;open capture "YAPP.IN"
;
;--------------------------------------------------------
;
; YAPP TX1 --> prepare file + send YPUT+info (alt-q)
st q0 \x:o byapt ;prepare outgoing file in DOS-shell with Byapt
st q1 \x:paclen 230 ;set paclen to normal
st q2 r yapp.snd ;send yapp request and file info
;
;
; YAPP TX2 --> reply to "Ready to recei...." (alt-w)
st w1 paclen 2 ;set paclen to 2 for next transmission
st w2 \x ;send ^E^A
;
; YAPP TX3 --> reply to ^F^A (send header) (alt-e)
st e0 \x:paclen 230 ;set paclen to normal
st e1 rprg yapp.hea ;send header info
;
; YAPP TX4 --> reply to ^F^B (send file) (alt-r)
st r \x:rprg yapp.out ;send prepared data file
;
; YAPP TX5 --> reply to ^F^C (send end_of_tx) (alt t)
st t0 \x:paclen 2 ;set paclen to 2 for next transmission
st t1 \x ;send ^D^A
st t2 \x:paclen 230 ;set paclen to normal
st t3 \x\rbug ;send dummy cmd to fbb to break looping (perhaps)